Method and device for updating a wait timer

ABSTRACT

Methods and apparatuses are disclosed for updating a wait timer as a result of receiving one of a release message and a suspend message and/or configuring a wireless device (WD) to update a wait timer by determining the one of the release message and the suspend message to be communicated to the WD.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/047,986 filed Oct. 15, 2020 entitled “METHOD AND DEVICE FOR UPDATINGA WAIT TIMER”, which is an application Under 35 U.S.C. § 371 for U.S.National Stage Patent Application of International Application No.:PCT/IB2019/053052, filed Apr. 12, 2019 entitled “HANDLING OF REJECT WAITTIME,” which claims priority to U.S. Provisional Application No.62/657,994, filed Apr. 16, 2018, entitled “HANDLING OF REJECT WAITTIME,” the entireties of all of which are incorporated herein byreference.

TECHNICAL FIELD

The present disclosure relates to wireless communications, and inparticular, to apparatuses and methods for handling a reject waitingtime.

BACKGROUND

Example Radio Resource Control (RRC) Connection Resume in Long-termEvolution (LTE)

In 3^(rd) Generation Partnership Project (3GPP) LTE Release 13 (Rel-13),a mechanism was introduced for a wireless device (WD) (e.g., userequipment (UE)) to be suspended by the network in a suspended statesimilar to RRC_IDLE but with the difference that the WD stores theAccess Stratum (AS) context or RRC context. This makes it possible toreduce the signaling when the WD is becoming active again by resumingthe RRC connection, instead of establishing the RRC connection fromscratch. Reducing the signaling could have several benefits, such as,reducing latency e.g., for smart phones accessing Internet and/orreduced signaling leading to reduced battery consumption formachine-type devices sending very little data.

Such Rel-13 solution is based on the WD sending aRRCConnectionResumeRequest message to the network and, in response, theWD receiving an RRCConnectionResume message from the network. TheRRCConnectionResume may not be encrypted but integrity may be protected.

RRC_INACTIVE in NR and Possibly in LTE Rel-15

As part of the standardized work on 5G New Radio (NR) in 3GPP, it hasbeen considered that NR should support an RRC_INACTIVE state withsimilar properties as the suspended state in LTE Rel-13. TheRRC_INACTIVE has slightly different properties from the later state inthat it is a separate RRC state and not part of RRC_IDLE as in LTE.Additionally, the CN/RAN connection (NG or N2 interface) may be kept forRRC_INACTIVE while it was suspended in LTE. FIG. 1 shows an example ofpossible state transitions in NR.

Some of the properties of the states shown in FIG. 1 may be as follows:

RRC_IDLE:

-   -   A WD-specific Discontinuous Reception (DRX) may be configured by        upper layers;    -   WD-controlled mobility based on network configuration;    -   The WD:        -   Monitors a Paging channel for Core Network (CN) paging using            5G-SAE-Temporary Mobile Subscriber Identity (S-TMSI);        -   Performs neighboring cell measurements and cell            (re-)selection; and        -   Acquires system information.

RRC_INACTIVE:

-   -   A WD-specific DRX may be configured by upper layers or by RRC        layer;    -   WD-controlled mobility based on network configuration;    -   The WD stores the AS context;    -   The WD:        -   Monitors a Paging channel for CN paging using 5G-S-TMSI and            Radio Access Network (RAN) paging using Information-Radio            Network Temporary Identifier (I-RNTI);        -   Performs neighboring cell measurements and cell            (re-)selection;        -   Performs RAN-based notification area updates periodically            and when moving outside the RAN-based notification area; and        -   Acquires system information.

RRC_CONNECTED:

-   -   The WD stores the AS context;    -   Transfer of unicast data to/from WD;    -   At lower layers, the WD may be configured with a WD-specific        DRX;    -   For WDs supporting Carrier Aggregation (CA), use of one or more        Secondary Cells (Scells), aggregated with the Primary Serving        Cell (SpCell), for increased bandwidth;    -   For WDs supporting Dual Connectivity (DC), use of one Secondary        Cell Group (SCG), aggregated with the Master Cell Group (MCG),        for increased bandwidth;    -   Network controlled mobility, i.e. handover within NR and to/from        Evolved-Universal Terrestrial Radio Access (E-UTRAN); and    -   The WD:        -   Monitors a Paging channel;        -   Monitors control channels associated with the shared data            channel to determine if data is scheduled for it;        -   Provides channel quality and feedback information;        -   Performs neighboring cell measurements and measurement            reporting; and        -   Acquires system information.

Reject Procedure in LTE (Overload Scenarios)

In LTE, the network can send an RRC Reject message with a wait timeeither in response to an RRC Resume Request (as shown in FIG. 2 ), e.g.,in the case of an overload condition, or in response to an RRCConnection Establishment (as shown in FIG. 3 ).

The Reject message may contain a wait time value and, upon receiving themessage, the WD initiates a timer called T302 and informs upper layers,as shown by the following excerpt from 3GPP Technical Specification (TS)36.331 shown as follows. According to the TS 36.331, Reception of theRRCConnectionReject by the WD may include that the WD can:

-   -   stop timer T300;    -   reset Media Access Control (MAC) and release the MAC        configuration;    -   except for Narrowband-Internet of Things (NB-IoT), start timer        T302, with the timer value set to the waitTime;    -   if the WD is a NB-IoT WD; or    -   if the extendedWaitTime is present and the WD supports delay        tolerant access:        -   forward the extendedWaitTime to upper layers;    -   if deprioritisationReq is included and the WD supports RRC        Connection Reject with deprioritisation:        -   start or restart timer T325 with the timer value set to the            deprioritisationTimer signalled;        -   store the deprioritisationReq until T325 expiry;    -   NOTE: The WD stores the deprioritisation request irrespective of        any cell reselection absolute priority assignments (by dedicated        or common signalling) and regardless of RRC connections in        E-UTRAN or other RATs unless specified otherwise.    -   if the RRCConnectionReject is received in response to an        RRCConnectionResumeRequest:        -   if the rrc-SuspendIndication is not present:            -   discard the stored WD AS context and resumeIdentity;            -   inform upper layers about the failure to resume the RRC                connection without suspend indication and that access                barring for mobile originating calls, mobile originating                signalling, mobile terminating access and except for                NB-IoT for mobile originating CS fallback is applicable,                upon which the procedure ends;        -   else:            -   suspend SRB1;            -   inform upper layers about the failure to resume the RRC                connection with suspend indication and that access                barring for mobile originating calls, mobile originating                signalling, mobile terminating access and except for                NB-IoT for mobile originating CS fallback is applicable,                upon which the procedure ends;    -   else:        -   inform upper layers about the failure to establish the RRC            connection and that access barring for mobile originating            calls, mobile originating signalling, mobile terminating            access and except for NB-IoT, for mobile originating CS            fallback is applicable, upon which the procedure ends.

Another aspect about T302 that has been defined in the technicalspecifications is the criteria to stop the T302 timer and WD actionsupon expiration of the timer. In LTE, the timer may be stopped eitherwhen the WD receives an RRCConnectionResume, or an RRCConnectionSetup,as shown below by the following excerpt from 3GPP TS 36.331.

The excerpt from 3GPP TS 36.331 is as follows:

-   -   Reception of the RRCConnectionSetup by the WD        -   NOTE: Prior to this, lower layer signalling is used to            allocate a C-RNTI. For further details see TS 36.321;    -   The WD can:    -   1> if the RRCConnectionSetup is received in response to an        RRCConnectionResumeRequest:        -   2> discard the stored WD AS context and resumeIdentity;        -   2> indicate to upper layers that the RRC connection resume            has been fallbacked;    -   1> perform the radio resource configuration procedure in        accordance with the received radioResourceConfigDedicated and as        specified in 5.3.10;    -   1> if stored, discard the cell reselection priority information        provided by the idleModeMobilityControlInfo or inherited from        another RAT;    -   1> if stored, discard the dedicated offset provided by the        redirectedCarrierOffsetDedicated;    -   1> stop timer T300;    -   1> stop timer T302, if running;    -   1> stop timer T303, if running;    -   1> stop timer T305, if running;    -   1> stop timer T306, if running;    -   1> stop timer T308, if running;    -   1> perform the actions as specified in 5.3.3.7;    -   1> stop timer T320, if running;    -   1> stop timer T350, if running;    -   1> perform the actions as specified in 5.6.12.4;    -   1> release rclwi-Configuration, if configured, as specified in        5.6.16.2;    -   1> stop timer T360, if running;    -   1> stop timer T322, if running;    -   1> enter RRC_CONNECTED;    -   1> stop the cell re-selection procedure;    -   1> consider the current cell to be the PCell;    -   1> set the content of RRCConnectionSetupComplete message as        follows:        -   2> if the RRCConnectionSetup is received in response to an            RRCConnectionResumeRequest:            -   3> if upper layers provide an S-TMSI:                -   4> set the s-TMSI to the value received from upper                    layers;        -   2> set the selectedPLMN-Identity to the PLMN selected by            upper layers (see TS 23.122, TS 24.301) from the PLMN(s)            included in the plmn-IdentityList in            SystemInformationBlockType1 (or            SystemInformationBlockType1-NB in NB-IoT);        -   2> if upper layers provide the ‘Registered MME’, include and            set the registeredMME as follows:            -   3> if the PLMN identity of the ‘Registered MME’ is                different from the PLMN selected by the upper layers:                -   4> include the plmnIdentity in the registeredMME and                    set it to the value of the PLMN identity in the                    ‘Registered MME’ received from upper layers;            -   3> set the mmegi and the mmec to the value received from                upper layers;        -   2> if upper layers provided the ‘Registered MME’:            -   3> include and set the gummei-Type to the value provided                by the upper layers;        -   2> if the WD supports CIoT EPS optimisation(s):            -   3> include attachWithoutPDN-Connectivity if received                from upper layers;            -   3> include up-CIoT-EPS-Optimisation if received from                upper layers;            -   3> except for NB-IoT, include cp-CIoT-EPS-Optimisation                if received from upper layers;        -   2> if connecting as an RN:            -   3> include the rn-SubframeConfigReq;        -   2> set the dedicatedInfoNAS to include the information            received from upper layers;        -   2> except for NB-IoT:            -   3> if the WD has radio link failure or handover failure                information available in VarRLF-Report and if the RPLMN                is included in plmn-IdentityList stored in                VarRLF-Report:                -   4> include rif-InfoAvailable;            -   3> if the WD has MBSFN logged measurements available for                E-UTRA and if the RPLMN is included in plmn-IdentityList                stored in VarLogMeasReport:                -   4> include logMeasAvailableMBSFN;            -   3> else if the WD has logged measurements available for                E-UTRA and if the RPLMN is included in plmn-IdentityList                stored in VarLogMeasReport:                -   4> include logMeasAvailable;            -   3> if the WD has connection establishment failure                information available in VarConnEstFailReport and if the                RPLMN is equal to plmnIdentity stored in                VarConnEstFailReport:                -   4> include connEstFailInfoAvailable;            -   3> include the mobilityState and set it to the mobility                state (as specified in TS 36.304) of the WD just prior                to entering RRC_CONNECTED state;            -   3> if the WD supports storage of mobility history                information and the WD has mobility history information                available in VarMobilityHistoryReport:                -   4> include the mobilityHistoryAvail;        -   2> include dcn-ID if a DCN-ID value (see TS 23.401) is            received from upper layers;        -   2> if WD needs UL gaps during continuous uplink            transmission:            -   3> include ue-CE-NeedULGaps;        -   2> submit the RRCConnectionSetupComplete message to lower            layers for transmission, upon which the procedure ends;    -   Reception of the RRCConnectionResume by the WD    -   The WD can:    -   1> stop timer T300;    -   1> restore the PDCP state and re-establish PDCP entities for        SRB2, if configured with E-UTRA PDCP, and for all DRBs that are        configured with E-UTRA PDCP;    -   1> if drb-ContinueROHC is included:        -   2> indicate to lower layers that stored WD AS context is            used and that drb-ContinueROHC is configured;        -   2> continue the header compression protocol context for the            DRBs configured with the header compression protocol;    -   1> else:        -   2> indicate to lower layers that stored WD AS context is            used;        -   2> reset the header compression protocol context for the            DRBs configured with the header compression protocol;    -   1> discard the stored WD AS context and resumeIdentity;    -   1> perform the radio resource configuration procedure in        accordance with the received radioResourceConfigDedicated and as        specified in 5.3.10;

NOTE: When performing the radio resource configuration procedure, forthe physical layer configuration and the MAC Main configuration, therestored RRC configuration from the stored WD AS context is used asbasis for the reconfiguration.

-   -   1> if the received RRCConnectionResume message includes the        sk-Counter:        -   2> perform key update procedure as specified in TS 38.331            [5.3.5.8];    -   1> if the received RRCConnectionResume message includes the        nr-RadioBearerConfig1:        -   2> perform radio bearer configuration as specified in TS            38.331 [5.3.5.6];    -   1> if the received RRCConnectionResume message includes the        nr-RadioBearerConfig2:        -   2> perform radio bearer configuration as specified in TS            38.331 [5.3.5.6];    -   1> resume SRB2 and all DRBs, if any, including RBs configured        with NR PDCP;    -   1> if stored, discard the cell reselection priority information        provided by the idleModeMobilityControlInfo or inherited from        another RAT;    -   1> if stored, discard the dedicated offset provided by the        redirectedCarrierOffsetDedicated;    -   1> if the RRCConnectionResume message includes the measConfig:        -   2> perform the measurement configuration procedure as            specified in 5.5.2;    -   1> stop timer T302, if running;    -   1> stop timer T303, if running;    -   1> stop timer T305, if running;    -   1> stop timer T306, if running;    -   1> stop timer T308, if running;    -   1> perform the actions as specified in 5.3.3.7;    -   1> stop timer T320, if running;    -   1> stop timer T350, if running;    -   1> perform the actions as specified in 5.6.12.4;    -   1> stop timer T360, if running;    -   1> stop timer T322, if running;    -   1> update the K_(eNB) key based on the K_(ASME) key to which the        current K_(eNB) is associated, using the nextHopChainingCount        value indicated in the RRCConnectionResume message, as specified        in TS 33.401;    -   1> store the nextHopChainingCount value;    -   1> derive the K_(RRCint) key associated with the previously        configured integrity algorithm, as specified in TS 33.401;    -   1> request lower layers to verify the integrity protection of        the RRCConnectionResume message, using the previously configured        algorithm and the K_(RRCint) key;    -   1> if the integrity protection check of the RRCConnectionResume        message fails:        -   2> perform the actions upon leaving RRC_CONNECTED as            specified in 5.3.12, with release cause ‘other’, upon which            the procedure ends;    -   1> derive the K_(RRCenc) key and the K_(UPenc) key associated        with the previously configured ciphering algorithm, as specified        in TS 33.401;    -   1> configure lower layers to resume integrity protection using        the previously configured algorithm and the K_(RRCint) key        immediately, i.e., integrity protection shall be applied to all        subsequent messages received and sent by the WD;    -   1> configure lower layers to resume ciphering and to apply the        ciphering algorithm, the K_(RRCenc) key and the K_(UPenc) key,        i.e. the ciphering configuration shall be applied to all        subsequent messages received and sent by the WD;    -   1> enter RRC_CONNECTED;    -   1> indicate to upper layers that the suspended RRC connection        has been resumed;    -   1> stop the cell re-selection procedure;    -   1> consider the current cell to be the PCell;    -   1> set the content of RRCConnectionResumeComplete message as        follows:        -   2> set the selectedPLMN-Identity to the PLMN selected by            upper layers (see TS 23.122, TS 24.301) from the PLMN(s)            included in the plmn-IdentityList in            SystemInformationBlockType1;        -   2> set the dedicatedInfoNAS to include the information            received from upper layers;        -   2> except for NB-IoT:            -   3> if the WD has radio link failure or handover failure                information available in VarRLF-Report and if the RPLMN                is included in plmn-IdentityList stored in                VarRLF-Report:                -   4> include rif-InfoAvailable;            -   3> if the WD has MBSFN logged measurements available for                E-UTRA and if the RPLMN is included in plmn-IdentityList                stored in VarLogMeasReport:                -   4> include logMeasAvailableMBSFN;            -   3> else if the WD has logged measurements available for                E-UTRA and if the RPLMN is included in plmn-IdentityList                stored in VarLogMeasReport:                -   4> include logMeasAvailable;            -   3> if the WD has connection establishment failure                information available in VarConnEstFailReport and if the                RPLMN is equal to plmnIdentity stored in                VarConnEstFailReport:                -   4> include connEstFailInfoAvailable;            -   3> include the mobilityState and set it to the mobility                state (as specified in TS 36.304) of the WD just prior                to entering RRC_CONNECTED state;            -   3> if the WD supports storage of mobility history                information and the WD has mobility history information                available in VarMobilityHistoryReport:                -   4> include mobilityHistoryAvail;    -   1> submit the RRCConnectionResumeComplete message to lower        layers for transmission;    -   1> the procedure ends.

Table 1 herein below is an example of a table defined in currentspecifications.

TABLE 1 Section 7.3.1 Timers (Informative) Timer Start Stop At expiryT300 Transmission of Reception of Perform the actions as NOTE1RRCConnectionRequest RRCConnectionSetup, specified in 5.3.3.6 orRRCConnectionReject or RRCConnection- RRCConnectionResume ResumeRequestmessage, cell re-selection and upon abortion of connection establishmentby upper layers T301 Transmission of Reception of Go to RRC_IDLE NOTE1RRCConnection- RRCConnectionReestablish- ReestabilshmentRequest ment orRRCConnectionReestablish- mentReject message as well as when theselected cell becomes unsuitable T302 Reception of Upon entering Informupper layers about RRCConnectionReject RRC_CONNECTED and barringalleviation as while upon cell re-selection specified in 5.3.3.7performing RRC connection establishment

Considerations on the Reject Procedure in NR

The Reject procedure has also been discussed for NR. In RAN2 #99bis, thefollowing has been considered:

-   -   A WD in INACTIVE, trying to resume an RRC connection, can        receive MSG4 sent over SRB0 (without Integrity protection) to        move the WD back into INACTIVE (i.e. rejected with wait timer).    -   INACTIVE related parameters/configuration should not be updated        by a MSG4 sent over SRB0 (as it is a non-protected message).

FIG. 4 illustrates an example of transitions from RRC_INACTIVE toRRC-INACTIVE in a rejection scenario.

Current Implementation on Reject Procedure to RRC NR Specifications

The Reject procedure is currently being considered. First, as in LTE,timer T302 may be started upon the reception of an RRCReject message,which can either be in response to an RRCResumeRequest orRRCSetupRequest, as the following excerpt of TS 38.331 shows: Receptionof the RRCReject by the WD—The WD can:

-   -   1> stop timer T300;    -   1> reset MAC and release the MAC configuration;    -   1> start timer T302, with the timer value set to the waitTime;    -   1> inform upper layers about the failure to establish the RRC        connection and access control related information, upon which        the procedure ends.

The access control related information may be informed to higher layers.

SUMMARY

Some embodiments advantageously provide methods and apparatuses forhandling a reject wait time or integrity errors associated with a waittimer that may advantageously e.g., avoid or reduce networkinefficiencies.

According to one aspect of the present disclosure, a method in awireless device, WD, is provided. The method comprises receiving, from anetwork node, one of a release message and a suspend message; andupdating a wait timer as a result of receiving the one of the releasemessage and the suspend message.

In some embodiments of this aspect, the wait timer is a T302 timer. Insome embodiments of this aspect, updating the wait timer as a result ofreceiving the one of the release message and the suspend message furthercomprises: stopping the wait timer responsive to receipt of the one ofthe release message and the suspend message. In some embodiments of thisaspect, updating the wait timer as a result of receiving the one of therelease message and the suspend message further comprises: updating thewait timer according to a wait value identified in the one of therelease message and the suspend message. In some embodiments of thisaspect, updating the wait timer as a result of receiving the one of therelease message and the suspend message further comprises: stopping thewait timer responsive to identifying an indicator within the one of therelease message and the suspend message, the indicator indicating thatthe wait timer should be stopped if running. In some embodiments of thisaspect, updating the wait timer as a result of receiving the one of therelease message and the suspend message further comprises: stopping thewait timer responsive to identifying an absence of an indicator withinthe one of the release message and the suspend message, the indicatorindicating that the wait timer should continue running if alreadyrunning. In some embodiments of this aspect, updating the wait timer asa result of receiving the one of the release message and the suspendmessage further comprises: restarting the wait timer responsive toreceipt of the one of the release message and the suspend message. Insome embodiments of this aspect, the one of the release message and thesuspend message is one of a Radio Resource Control, RRC, Release messageand a RRC Suspend message. In some embodiments of this aspect, themethod further comprises communicating, to the network node, a resumerequest message, wherein the one of the release message and the suspendmessage is received as a result of communicating the resume requestmessage.

According to another aspect of the present disclosure, a method in awireless device, WD, comprises detecting an integrity protectionverification error in a lower layer while a wait timer is running; andupdating the wait timer as a result of the detection of the integrityprotection verification error.

In some embodiments of this aspect, the wait timer is a T302 timer. Insome embodiments of this aspect, updating the wait timer as a result ofthe detection of the integrity protection verification error furthercomprises: stopping the wait timer responsive to the detection of theintegrity protection verification error. In some embodiments of thisaspect, updating the wait timer as a result of the detection of theintegrity protection verification error further comprises: restartingthe wait timer responsive to the detection of the integrity protectionverification error. In some embodiments of this aspect, detecting theintegrity protection verification error in the lower layer while thewait timer is running further comprises at least one of: detecting thata T300X timer expired and detecting an integrity check failure while theT300X timer is running.

In yet another aspect of the present disclosure, a method in a networknode configured to communicate with a wireless device, WD, is provided.The method comprises receiving, from the WD, a resume request message;and determining one of a release message and a suspend message to becommunicated to the WD as a result of receiving the resume requestmessage, the one of the release message and the suspend messageconfiguring a wait timer of the WD.

In some embodiments of this aspect, the one of the release message andthe suspend message is one of a Radio Resource Control, RRC, Releasemessage and a RRC Suspend message. In some embodiments of this aspect,the wait timer is a T302 timer. In some embodiments of this aspect,determining the one of the release message and the suspend message toconfigure the wait timer of the WD further comprises: configuring thewait timer of the WD to stop responsive to receipt of the one of therelease message and the suspend message. In some embodiments of thisaspect, determining the one of the release message and the suspendmessage to configure the wait timer of the WD further comprises:configuring the wait timer of the WD to update the wait timer accordingto a wait value included in the one of the release message and thesuspend message. In some embodiments of this aspect, determining the oneof the release message and the suspend message to configure the waittimer of the WD further comprises: configuring the wait timer of the WDto stop responsive to identifying an indicator within the one of therelease message and the suspend message, the indicator indicating thatthe wait timer should be stopped if running. In some embodiments of thisaspect, determining the one of the release message and the suspendmessage to configure the wait timer of the WD further comprises:configuring the wait timer of the WD to stop responsive to identifyingan absence of an indicator within the one of the release message and thesuspend message, the indicator indicating that the wait timer shouldcontinue running if already running. In some embodiments of this aspect,determining the one of the release message and the suspend message toconfigure the wait timer of the WD further comprises: configuring thewait timer of the WD to restart the wait timer responsive to receipt ofthe one of the release message and the suspend message. In someembodiments of this aspect, the method further comprises, as a result ofreceiving the resume request message, communicating the one of therelease message and the suspend message to the WD.

According to yet another aspect of the present disclosure, a wirelessdevice, WD, configured to communicate with a network node is provided.The WD comprises processing circuitry, the processing circuitryconfigured to: receive, from the network node, one of a release messageand a suspend message; and update a wait timer as a result of receivingthe one of the release message and the suspend message.

In some embodiments of this aspect, the wait timer is a T302 timer. Insome embodiments of this aspect, the processing circuitry is furtherconfigured to update the wait timer as a result of receiving the one ofthe release message and the suspend message by being configured to: stopthe wait timer responsive to receipt of the one of the release messageand the suspend message. In some embodiments of this aspect, theprocessing circuitry is further configured to update the wait timer as aresult of receiving the one of the release message and the suspendmessage by being configured to: update the wait timer according to await value identified in the one of the release message and the suspendmessage. In some embodiments of this aspect, the processing circuitry isfurther configured to update the wait timer as a result of receiving theone of the release message and the suspend message by being configuredto: stop the wait timer responsive to identifying an indicator withinthe one of the release message and the suspend message, the indicatorindicating that the wait timer should be stopped if running. In someembodiments of this aspect, the processing circuitry is furtherconfigured to update the wait timer as a result of receiving the one ofthe release message and the suspend message by being configured to: stopthe wait timer responsive to identifying an absence of an indicatorwithin the one of the release message and the suspend message, theindicator indicating that the wait timer should continue running ifalready running. In some embodiments of this aspect, the processingcircuitry is further configured to update the wait timer as a result ofreceiving the one of the release message and the suspend message bybeing configured to: restart the wait timer responsive to receipt of theone of the release message and the suspend message. In some embodimentsof this aspect, the one of the release message and the suspend messageis one of a Radio Resource Control, RRC, Release message and a RRCSuspend message. In some embodiments of this aspect, the processingcircuitry is further configured to: communicate, to the network node, aresume request message, wherein the one of the release message and thesuspend message is received as a result of communicating the resumerequest message.

According to another aspect of the present disclosure, a wirelessdevice, WD, configured to communicate with a network node is provided.The WD comprises processing circuitry, the processing circuitryconfigured to: detect an integrity protection verification error in alower layer while a wait timer is running; and update the wait timer asa result of the detection of the integrity protection verificationerror.

In some embodiments of this aspect, the wait timer is a T302 timer. Insome embodiments of this aspect, the processing circuitry is furtherconfigured to update the wait timer as a result of the detection of theintegrity protection verification error by being configured to: stop thewait timer responsive to the detection of the integrity protectionverification error. In some embodiments of this aspect, the processingcircuitry is further configured to update the wait timer as a result ofthe detection of the integrity protection verification error by beingconfigured to: restart the wait timer responsive to the detection of theintegrity protection verification error. In some embodiments of thisaspect, the processing circuitry is further configured to detect theintegrity protection verification error in the lower layer while thewait timer is running by being configured to at least one of: detectthat a T300X timer expired and detect an integrity check failure whilethe T300X timer is running.

According to yet another aspect of the present disclosure, a networknode configured to communicate with a wireless device, WD, is provided.The network node comprises processing circuitry, the processingcircuitry configured to: receive, from the WD, a resume request message;and determine one of a release message and a suspend message to becommunicated to the WD as a result of receiving the resume requestmessage, the one of the release message and the suspend messageconfiguring a wait timer of the WD.

In some embodiments of this aspect, the one of the release message andthe suspend message is one of a Radio Resource Control, RRC, Releasemessage and a RRC Suspend message. In some embodiments of this aspect,the wait timer is a T302 timer. In some embodiments of this aspect, theprocessing circuitry is further configured to determine the one of therelease message and the suspend message to configure the wait timer ofthe WD by being configured to: configure the wait timer of the WD tostop responsive to receipt of the one of the release message and thesuspend message. In some embodiments of this aspect, the processingcircuitry is further configured to determine the one of the releasemessage and the suspend message to configure the wait timer of the WD bybeing configured to: configure the wait timer of the WD to update thewait timer according to a wait value included in the one of the releasemessage and the suspend message. In some embodiments of this aspect, theprocessing circuitry is further configured to determine the one of therelease message and the suspend message to configure the wait timer ofthe WD by being configured to: configure the wait timer of the WD tostop responsive to identifying an indicator within the one of therelease message and the suspend message, the indicator indicating thatthe wait timer should be stopped if running. In some embodiments of thisaspect, the processing circuitry is further configured to determine theone of the release message and the suspend message to configure the waittimer of the WD by being configured to: configure the wait timer of theWD to stop responsive to identifying an absence of an indicator withinthe one of the release message and the suspend message, the indicatorindicating that the wait timer should continue running if alreadyrunning. In some embodiments of this aspect, the processing circuitry isfurther configured to determine the one of the release message and thesuspend message to configure the wait timer of the WD by beingconfigured to: configure the wait timer of the WD to restart the waittimer responsive to receipt of the one of the release message and thesuspend message. In some embodiments of this aspect, the processingcircuitry is further configured to, as a result of receiving the resumerequest message, communicate the one of the release message and thesuspend message to the WD.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments, and theattendant advantages and features thereof, will be more readilyunderstood by reference to the following detailed description whenconsidered in conjunction with the accompanying drawings wherein:

FIG. 1 illustrates an example WD state machine and state transitions inNR;

FIG. 2 illustrates an RRC connection resume request resulting in anetwork reject or release;

FIG. 3 illustrates an RRC connection establishment request resulting ina network reject;

FIG. 4 illustrates transitions from RRC_INACTIVE to RRC_INACTIVE in arejection scenario;

FIG. 5 illustrates RRC connection resume requests resulting in anRRCSuspend or RRCRelease message;

FIG. 6 is a schematic diagram of an exemplary network architectureillustrating a communication system connected via an intermediatenetwork to a host computer according to the principles in the presentdisclosure;

FIG. 7 is a block diagram of a host computer communicating via a networknode with a wireless device over an at least partially wirelessconnection according to some embodiments of the present disclosure;

FIG. 8 is a flowchart of an exemplary process in a network node forhandling a reject wait time according to some embodiments of the presentdisclosure;

FIG. 9 is a flowchart of an exemplary process in a wireless device forhandling a reject wait time according to some embodiments of the presentdisclosure; and

FIG. 10 is a flowchart of yet another exemplary process in a wirelessdevice for updating a wait timer according to some embodiments of thepresent disclosure.

DETAILED DESCRIPTION

In NR, timer T302 can be stopped, if running, when the WD entersRRC_CONNECTED i.e., upon receiving an RRCSetup or/and RRCResume message.

Some of the following aspects have been considered for NR RRC, which aredifferent from LTE RRC:

-   -   In NR RRC, the network may respond to a ResumeRequest from the        WD with a Suspend message which immediately orders the WD back        to RRC_INACTIVE state. In LTE, it is not possible to send a        suspend message (Release with suspend indication) directly to        the WD trying to resume the connection (as shown for example in        a comparison of FIG. 3 (LTE) with FIG. 5 (NR)).    -   In NR RRC, the network may respond to a ResumeRequest from the        WD with a Release message that immediately orders the WD back to        RRC_IDLE state. Also, this message may be encrypted. In LTE, it        is not possible to send a release message (Release) directly to        the WD trying to resume the connection (as shown for example in        a comparison of FIG. 3 (LTE) with FIG. 5 (NR)).

The scenario described above may be useful for e.g. during RAN areaupdates, which can be triggered by the expiration of the periodic RNA(Radio Access Network Notification Area) timer. That may also bepossible in other scenarios, e.g., in Rel-16, during small/early datatransmission. It may be considered in NR, that depending on the handlingof barring, the WD may initiate an RRC Resume procedure while wait timerT302 is running.

Hence, due to the differences above, i.e., the new possible responses inNR (Suspend or Release), the timer T302 according to existing procedureswill keep running. And, even though the network has already provided aRelease message (or suspend), the WD may perform actions upon T302expiry when not needed.

The consequence is that the network may not be overloaded anymore,although WD may keep running T302 as if the network is overloaded.Hence, if after receiving the Release or Suspend message the WD has someUplink (UL) data to transmit, the WD could not do that, as T302 wouldstill be running despite the network not being overloaded anymore. Inthis case, the WD may not be able to access the network.

Another scenario could be that the WD is paged while T302 is running. Inthis case, the WD may respond to the page assuming page responseprocedures have high priority and can be performed when T302 is running.If the network at this stage decides to re-suspend or possibly releasethe WD the T302 will continue to run although this may not be desirablefrom the network point of view.

Accordingly, some embodiments of the disclosure introduce a newmechanism or triggers at a WD for stopping a wait timer and/or to updatethe value of the wait timer during RRC inactive procedures. In this way,the WD may not need to unnecessarily execute the procedure when the waittimer times out. The mechanism can be implicit e.g., based on thereception of Release or Suspend message, or the network can explicitlysignal the expected WD behavior e.g. reset the timer, stop the timer,continue to run the timer, or set the timer to a different value, etc.

Some advantages of embodiments of the present disclosure may includethat by using the new mechanism/triggers stopping (pausing, resetting,changing, continuing, or otherwise updating, etc.) the timer, it may bepossible to avoid performing the procedure when the timer times out,which could generate more signaling in the network, consume more WDbattery as well as create unnecessary interference. In some of theembodiments, more flexibility to the network may be provided to updatethe wait timer values according to overload conditions. In this way itmay be possible to prioritize emergency or critical communications overother non-critical communications, which could have an important benefitto society, emergency responders, etc. Before describing in detailexemplary embodiments, it is noted that the embodiments reside primarilyin combinations of apparatus components and processing steps related tohandling a reject wait time. Accordingly, components have beenrepresented where appropriate by conventional symbols in the drawings,showing only those specific details that are pertinent to understandingthe embodiments so as not to obscure the disclosure with details thatwill be readily apparent to those of ordinary skill in the art havingthe benefit of the description herein. Like numbers refer to likeelements throughout the description.

As used herein, relational terms, such as “first” and “second,” “top”and “bottom,” and the like, may be used solely to distinguish one entityor element from another entity or element without necessarily requiringor implying any physical or logical relationship or order between suchentities or elements. The terminology used herein is for the purpose ofdescribing particular embodiments only and is not intended to belimiting of the concepts described herein. As used herein, the singularforms “a”, “an” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will be furtherunderstood that the terms “comprises,” “comprising,” “includes” and/or“including” when used herein, specify the presence of stated features,integers, steps, operations, elements, and/or components, but do notpreclude the presence or addition of one or more other features,integers, steps, operations, elements, components, and/or groupsthereof.

In embodiments described herein, the joining term, “in communicationwith” and the like, may be used to indicate electrical or datacommunication, which may be accomplished by physical contact, induction,electromagnetic radiation, radio signaling, infrared signaling oroptical signaling, for example. One having ordinary skill in the artwill appreciate that multiple components may interoperate andmodifications and variations are possible of achieving the electricaland data communication.

In some embodiments described herein, the term “coupled,” “connected,”and the like, may be used herein to indicate a connection, although notnecessarily directly, and may include wired and/or wireless connections.

The term “network node” used herein can be any kind of network nodecomprised in a radio network which may further comprise any of basestation (BS), radio base station, base transceiver station (BTS), basestation controller (BSC), radio network controller (RNC), g Node B(gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio(MSR) radio node such as MSR BS, multi-cell/multicast coordinationentity (MCE), relay node, donor node controlling relay, integratedaccess and backhaul (IAB) node, radio access point (AP), transmissionpoints, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head(RRH), a core network node (e.g., mobile management entity (MME),self-organizing network (SON) node, a coordinating node, positioningnode, MDT node, etc.), an external node (e.g., 3rd party node, a nodeexternal to the current network), nodes in distributed antenna system(DAS), a spectrum access system (SAS) node, an element management system(EMS), etc. The network node may also comprise test equipment. The term“radio node” used herein may be used to also denote a wireless device(WD) such as a wireless device (WD) or a radio network node.

In some embodiments, the non-limiting terms wireless device (WD) or auser equipment (UE) are used interchangeably. The WD herein can be anytype of wireless device capable of communicating with a network node oranother WD over radio signals, such as wireless device (WD). The WD mayalso be a radio communication device, target device, device to device(D2D) WD, machine type WD or WD capable of machine to machinecommunication (M2M), low-cost and/or low-complexity WD, a sensorequipped with WD, Tablet, mobile terminals, smart phone, laptop embeddedequipped (LEE), laptop mounted equipment (LME), USB dongles, CustomerPremises Equipment (CPE), an Internet of Things (IoT) device, or aNarrowband IoT (NB-IOT) device etc.

Also, in some embodiments the generic term “radio network node” is used.It can be any kind of a radio network node which may comprise any ofbase station, radio base station, base transceiver station, base stationcontroller, network controller, RNC, evolved Node B (eNB), Node B, gNB,Multi-cell/multicast Coordination Entity (MCE), relay node, IAB node,access point, radio access point, Remote Radio Unit (RRU) Remote RadioHead (RRH).

Note that although terminology from one particular wireless system, suchas, for example, 3GPP LTE and/or New Radio (NR), may be used in thisdisclosure, this should not be seen as limiting the scope of thedisclosure to only the aforementioned system. Other wireless systems,including without limitation Wide Band Code Division Multiple Access(WCDMA), Worldwide Interoperability for Microwave Access (WiMax), UltraMobile Broadband (UMB) and Global System for Mobile Communications(GSM), may also benefit from exploiting the ideas covered within thisdisclosure.

Note further, that functions described herein as being performed by awireless device or a network node may be distributed over a plurality ofwireless devices and/or network nodes. In other words, it iscontemplated that the functions of the network node and wireless devicedescribed herein are not limited to performance by a single physicaldevice and, in fact, can be distributed among several physical devices.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which this disclosure belongs. It willbe further understood that terms used herein should be interpreted ashaving a meaning that is consistent with their meaning in the context ofthis specification and the relevant art and will not be interpreted inan idealized or overly formal sense unless expressly so defined herein.

In some embodiments, methods are described as actions performed by anRRC_INACTIVE WD in NR. While some embodiments are applicable for thatcase, there can be other additional cases for which embodiments areapplicable such as:

-   -   All previous cases where procedures occur in LTE instead of NR;        that is for the case of LTE RRC_INACTIVE WDs;    -   Inter-radio access technology (RAT) procedures in the        RRC_INACTIVE state, mainly between LTE and NR connected to the        same CN (5G Core Network):        -   the WD in LTE RRC_CONNECTED state is suspended to LTE            RRC_INACTIVE state and starts T380, performs mobility and            camps on an NR cell (i.e., becomes in NR RRC_INACTIVE state)            and tries to resume in NR while T380 is running.        -   the WD in NR RRC_CONNECTED state is suspended to NR            RRC_INACTIVE state and starts T380, performs mobility and            camps on an LTE cell (i.e., transits to LTE RRC_INACTIVE            state) and tries to resume in LTE while T380 is running.

Embodiments provide apparatuses and methods for the management of a waittimer in a WD 22 when performing RRC connection resume. In someembodiments, by using a new mechanism/trigger for stopping (pausing,resuming, resetting, changing or otherwise updating, etc.) the waittimer it may be possible to avoid performing the procedure when thetimer times out, which could generate more signaling in the network,consume more WD 22 battery, as well as, creating unnecessaryinterference. In some of the embodiments, more flexibility to thenetwork may be provided to update the wait timer values of WDs 22according to e.g., overload conditions. In this way, it may be possibleto prioritize emergency or critical communications over othernon-critical communications, which could have an important benefit tosociety, emergency responders, etc.

Returning to the drawing figures, in which like elements are referred toby like reference numerals, there is shown in FIG. 6 a schematic diagramof a communication system 10, according to an embodiment, such as a3GPP-type cellular network that may support standards such as LTE and/orNR (5G), which comprises an access network 12, such as a radio accessnetwork, and a core network 14. The access network 12 comprises aplurality of network nodes 16 a, 16 b, 16 c (referred to collectively asnetwork nodes 16), such as NBs, eNBs, gNBs or other types of wirelessaccess points, each defining a corresponding coverage area 18 a, 18 b,18 c (referred to collectively as coverage areas 18). Each network node16 a, 16 b, 16 c is connectable to the core network 14 over a wired orwireless connection 20. A first wireless device (WD) 22 a located incoverage area 18 a is configured to wirelessly connect to, or be pagedby, the corresponding network node 16 c. A second WD 22 b in coveragearea 18 b is wirelessly connectable to the corresponding network node 16a. While a plurality of WDs 22 a, 22 b (collectively referred to aswireless devices 22) are illustrated in this example, the disclosedembodiments are equally applicable to a situation where a sole WD is inthe coverage area or where a sole WD is connecting to the correspondingnetwork node 16. Note that although only two WDs 22 and three networknodes 16 are shown for convenience, the communication system may includemany more WDs 22 and network nodes 16.

Also, it is contemplated that a WD 22 can be in simultaneouscommunication and/or configured to separately communicate with more thanone network node 16 and more than one type of network node 16. Forexample, a WD 22 can have dual connectivity with a network node 16 thatsupports LTE and the same or a different network node 16 that supportsNR. As an example, WD 22 can be in communication with an eNB forLTE/E-UTRAN and a gNB for NR/NG-RAN.

The communication system 10 may itself be connected to a host computer24, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. The host computer 24 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider. Theconnections 26, 28 between the communication system 10 and the hostcomputer 24 may extend directly from the core network 14 to the hostcomputer 24 or may extend via an optional intermediate network 30. Theintermediate network 30 may be one of, or a combination of more than oneof, a public, private or hosted network. The intermediate network 30, ifany, may be a backbone network or the Internet. In some embodiments, theintermediate network 30 may comprise two or more sub-networks (notshown).

The communication system of FIG. 6 as a whole enables connectivitybetween one of the connected WDs 22 a, 22 b and the host computer 24.The connectivity may be described as an over-the-top (OTT) connection.The host computer 24 and the connected WDs 22 a, 22 b are configured tocommunicate data and/or signaling via the OTT connection, using theaccess network 12, the core network 14, any intermediate network 30 andpossible further infrastructure (not shown) as intermediaries. The OTTconnection may be transparent in the sense that at least some of theparticipating communication devices through which the OTT connectionpasses are unaware of routing of uplink and downlink communications. Forexample, a network node 16 may not or need not be informed about thepast routing of an incoming downlink communication with data originatingfrom a host computer 24 to be forwarded (e.g., handed over) to aconnected WD 22 a. Similarly, the network node 16 need not be aware ofthe future routing of an outgoing uplink communication originating fromthe WD 22 a towards the host computer 24.

A network node 16 is configured to include a configuration unit 32 whichis configured to receive, from the WD 22, a resume request message; anddetermine one of a release message and a suspend message to becommunicated to the WD 22 as a result of receiving the resume requestmessage, the one of the release message and the suspend messageconfiguring a wait timer of the WD 22. A wireless device 22 isconfigured to include a timer controller unit 34 which is configured toreceive, from the network node 16, one of a release message and asuspend message; and update a wait timer as a result of receiving theone of the release message and the suspend message. In anotherembodiment, the wireless device 22 is configured to include a timercontroller unit 34 which is configured to detect an integrity protectionverification error in a lower layer while a wait timer is running; andupdate the wait timer as a result of the detection of the integrityprotection verification error.

Example implementations, in accordance with an embodiment, of the WD 22,network node 16 and host computer 24 discussed in the precedingparagraphs will now be described with reference to FIG. 7 . In acommunication system 10, a host computer 24 comprises hardware (HW) 38including a communication interface 40 configured to set up and maintaina wired or wireless connection with an interface of a differentcommunication device of the communication system 10. The host computer24 further comprises processing circuitry 42, which may have storageand/or processing capabilities. The processing circuitry 42 may includea processor 44 and memory 46. In particular, in addition to or insteadof a processor, such as a central processing unit, and memory, theprocessing circuitry 42 may comprise integrated circuitry for processingand/or control, e.g., one or more processors and/or processor coresand/or FPGAs (Field Programmable Gate Array) and/or ASICs (ApplicationSpecific Integrated Circuitry) adapted to execute instructions. Theprocessor 44 may be configured to access (e.g., write to and/or readfrom) memory 46, which may comprise any kind of volatile and/ornonvolatile memory, e.g., cache and/or buffer memory and/or RAM (RandomAccess Memory) and/or ROM (Read-Only Memory) and/or optical memoryand/or EPROM (Erasable Programmable Read-Only Memory).

Processing circuitry 42 may be configured to control any of the methodsand/or processes described herein and/or to cause such methods, and/orprocesses to be performed, e.g., by host computer 24. Processor 44corresponds to one or more processors 44 for performing host computer 24functions described herein. The host computer 24 includes memory 46 thatis configured to store data, programmatic software code and/or otherinformation described herein. In some embodiments, the software 48and/or the host application 50 may include instructions that, whenexecuted by the processor 44 and/or processing circuitry 42, causes theprocessor 44 and/or processing circuitry 42 to perform the processesdescribed herein with respect to host computer 24. The instructions maybe software associated with the host computer 24.

The software 48 may be executable by the processing circuitry 42. Thesoftware 48 includes a host application 50. The host application 50 maybe operable to provide a service to a remote user, such as a WD 22connecting via an OTT connection 52 terminating at the WD 22 and thehost computer 24. In providing the service to the remote user, the hostapplication 50 may provide user data which is transmitted using the OTTconnection 52. The “user data” may be data and information describedherein as implementing the described functionality. In one embodiment,the host computer 24 may be configured for providing control andfunctionality to a service provider and may be operated by the serviceprovider or on behalf of the service provider. The processing circuitry42 of the host computer 24 may enable the host computer 24 to observe,monitor, control, transmit to and/or receive from the network node 16and/or the wireless device 22. The processing circuitry 42 of the hostcomputer 24 may include a communication unit 54 configured to enable theservice provider to observe/monitor/control/transmit to/receive from thenetwork node 16 and/or the wireless device 22.

The communication system 10 further includes a network node 16 providedin a communication system 10 and comprising hardware 58 enabling it tocommunicate with the host computer 24 and with the WD 22. The hardware58 may include a communication interface 60 for setting up andmaintaining a wired or wireless connection with an interface of adifferent communication device of the communication system 10, as wellas a radio interface 62 for setting up and maintaining at least awireless connection 64 with a WD 22 located in a coverage area 18 servedby the network node 16. The radio interface 62 may be formed as or mayinclude, for example, one or more RF transmitters, one or more RFreceivers, and/or one or more RF transceivers. The communicationinterface 60 may be configured to facilitate a connection 66 to the hostcomputer 24. The connection 66 may be direct or it may pass through acore network 14 of the communication system 10 and/or through one ormore intermediate networks 30 outside the communication system 10.

In the embodiment shown, the hardware 58 of the network node 16 furtherincludes processing circuitry 68. The processing circuitry 68 mayinclude a processor 70 and a memory 72. In particular, in addition to orinstead of a processor, such as a central processing unit, and memory,the processing circuitry 68 may comprise integrated circuitry forprocessing and/or control, e.g., one or more processors and/or processorcores and/or FPGAs (Field Programmable Gate Array) and/or ASICs(Application Specific Integrated Circuitry) adapted to executeinstructions. The processor 70 may be configured to access (e.g., writeto and/or read from) the memory 72, which may comprise any kind ofvolatile and/or nonvolatile memory, e.g., cache and/or buffer memoryand/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/oroptical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the network node 16 further has software 74 stored internally in,for example, memory 72, or stored in external memory (e.g., database,storage array, network storage device, etc.) accessible by the networknode 16 via an external connection. The software 74 may be executable bythe processing circuitry 68. The processing circuitry 68 may beconfigured to control any of the methods and/or processes describedherein and/or to cause such methods, and/or processes to be performed,e.g., by network node 16. Processor 70 corresponds to one or moreprocessors 70 for performing network node 16 functions described herein.The memory 72 is configured to store data, programmatic software codeand/or other information described herein. In some embodiments, thesoftware 74 may include instructions that, when executed by theprocessor 70 and/or processing circuitry 68, causes the processor 70and/or processing circuitry 68 to perform the processes described hereinwith respect to network node 16. For example, processing circuitry 68 ofthe network node 16 may include configuration unit 32 configured toreceive, from the WD 22, a resume request message; and determine one ofa release message and a suspend message to be communicated to the WD 22as a result of receiving the resume request message, the one of therelease message and the suspend message configuring a wait timer of theWD 22.

In some embodiments, the one of the release message and the suspendmessage is one of: a Radio Resource Control (RRC) release message, a RRCsuspend message, and a RRC release message with suspend indication. Insome embodiments, the wait timer is a T302 timer. In some embodiments,the processing circuitry 68 is configured to determine the one of therelease message and the suspend message to configure the wait timer ofthe WD 22 to at least one of: stop the wait timer responsive to receiptof the one of the release message and the suspend message; stop the waittimer responsive to identifying an indicator within the one of therelease message and the suspend message, the indicator indicating thatthe wait timer should be stopped if running; stop the wait timerresponsive to identifying an absence of an indicator within the one ofthe release message and the suspend message, the indicator indicatingthat the wait timer should continue running if already running; updatethe wait timer according to a wait value identified in the one of therelease message and the suspend message; restart the wait timerresponsive to receipt of the one of the release message and the suspendmessage; and update the wait timer as a result of a detection of anintegrity protection verification error.

The communication system 10 further includes the WD 22 already referredto. The WD 22 may have hardware 80 that may include a radio interface 82configured to set up and maintain a wireless connection 64 with anetwork node 16 serving a coverage area 18 in which the WD 22 iscurrently located. The radio interface 82 may be formed as or mayinclude, for example, one or more RF transmitters, one or more RFreceivers, and/or one or more RF transceivers.

The hardware 80 of the WD 22 further includes processing circuitry 84.The processing circuitry 84 may include a processor 86 and memory 88. Inparticular, in addition to or instead of a processor, such as a centralprocessing unit, and memory, the processing circuitry 84 may compriseintegrated circuitry for processing and/or control, e.g., one or moreprocessors and/or processor cores and/or FPGAs (Field Programmable GateArray) and/or ASICs (Application Specific Integrated Circuitry) adaptedto execute instructions. The processor 86 may be configured to access(e.g., write to and/or read from) memory 88, which may comprise any kindof volatile and/or nonvolatile memory, e.g., cache and/or buffer memoryand/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/oroptical memory and/or EPROM (Erasable Programmable Read-Only Memory).

Thus, the WD 22 may further comprise software 90, which is stored in,for example, memory 88 at the WD 22, or stored in external memory (e.g.,database, storage array, network storage device, etc.) accessible by theWD 22. The software 90 may be executable by the processing circuitry 84.The software 90 may include a client application 92. The clientapplication 92 may be operable to provide a service to a human ornon-human user via the WD 22, with the support of the host computer 24.In the host computer 24, an executing host application 50 maycommunicate with the executing client application 92 via the OTTconnection 52 terminating at the WD 22 and the host computer 24. Inproviding the service to the user, the client application 92 may receiverequest data from the host application 50 and provide user data inresponse to the request data. The OTT connection 52 may transfer boththe request data and the user data. The client application 92 mayinteract with the user to generate the user data that it provides.

The processing circuitry 84 may be configured to control any of themethods and/or processes described herein and/or to cause such methods,and/or processes to be performed, e.g., by WD 22. The processor 86corresponds to one or more processors 86 for performing WD 22 functionsdescribed herein. The WD 22 includes memory 88 that is configured tostore data, programmatic software code and/or other informationdescribed herein. In some embodiments, the software 90 and/or the clientapplication 92 may include instructions that, when executed by theprocessor 86 and/or processing circuitry 84, causes the processor 86and/or processing circuitry 84 to perform the processes described hereinwith respect to WD 22. For example, the processing circuitry 84 of thewireless device 22 may include a timer controller unit 34 configured toreceive, from the network node 16, one of a release message and asuspend message; and update a wait timer as a result of receiving theone of the release message and the suspend message. In anotherembodiment, the processing circuitry 84 of the wireless device 22 mayinclude a timer controller unit 34 configured to detect an integrityprotection verification error in a lower layer while a wait timer isrunning; and update the wait timer as a result of the detection of theintegrity protection verification error.

In some embodiments, the processing circuitry 84 is further configuredto: communicate, to the network node 16, a resume request message, theone of the release message and the suspend message received as a resultof communicating the resume request message. In some embodiments, theone of the release message and the suspend message is one of: a RadioResource Control (RRC) release message, a RRC suspend message, and a RRCrelease message with suspend indication. In some embodiments, the waittimer is a T302 timer. In some embodiments, the processing circuitry 84is configured to update the wait timer as a result of receiving the oneof the release message and the suspend message by being furtherconfigured to at least one of: stop the wait timer responsive to receiptof the one of the release message and the suspend message; stop the waittimer responsive to identifying an indicator within the one of therelease message and the suspend message, the indicator indicating thatthe wait timer should be stopped if running; stop the wait timerresponsive to identifying an absence of an indicator within the one ofthe release message and the suspend message, the indicator indicatingthat the wait timer should continue running if already running; updatethe wait timer according to a wait value identified in the one of therelease message and the suspend message; and restart the wait timerresponsive to receipt of the one of the release message and the suspendmessage. In some embodiments, the processing circuitry 84 is furtherconfigured to: detect an integrity protection verification error in alower layer while the wait timer is running; and update the wait timeras a result of the detection of the integrity protection verificationerror.

In some embodiments, the inner workings of the network node 16, WD 22,and host computer 24 may be as shown in FIG. 7 and independently, thesurrounding network topology may be that of FIG. 6 .

In FIG. 7 , the OTT connection 52 has been drawn abstractly toillustrate the communication between the host computer 24 and thewireless device 22 via the network node 16, without explicit referenceto any intermediary devices and the precise routing of messages viathese devices. Network infrastructure may determine the routing, whichit may be configured to hide from the WD 22 or from the service provideroperating the host computer 24, or both. While the OTT connection 52 isactive, the network infrastructure may further take decisions by whichit dynamically changes the routing (e.g., on the basis of load balancingconsideration or reconfiguration of the network).

The wireless connection 64 between the WD 22 and the network node 16 isin accordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to the WD 22 using the OTTconnection 52, in which the wireless connection 64 may form the lastsegment. More precisely, the teachings of some of these embodiments mayimprove the data rate, latency, and/or power consumption and therebyprovide benefits such as reduced user waiting time, relaxed restrictionon file size, better responsiveness, extended battery lifetime, etc.

In some embodiments, a measurement procedure may be provided for thepurpose of monitoring data rate, latency and other factors on which theone or more embodiments improve. There may further be an optionalnetwork functionality for reconfiguring the OTT connection 52 betweenthe host computer 24 and WD 22, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring the OTT connection 52 may be implementedin the software 48 of the host computer 24 or in the software 90 of theWD 22, or both. In embodiments, sensors (not shown) may be deployed inor in association with communication devices through which the OTTconnection 52 passes; the sensors may participate in the measurementprocedure by supplying values of the monitored quantities exemplifiedabove, or supplying values of other physical quantities from whichsoftware 48, 90 may compute or estimate the monitored quantities. Thereconfiguring of the OTT connection 52 may include message format,retransmission settings, preferred routing etc.; the reconfiguring neednot affect the network node 16, and it may be unknown or imperceptibleto the network node 16. Some such procedures and functionalities may beknown and practiced in the art. In certain embodiments, measurements mayinvolve proprietary WD signaling facilitating the host computer's 24measurements of throughput, propagation times, latency and the like. Insome embodiments, the measurements may be implemented in that thesoftware 48, 90 causes messages to be transmitted, in particular emptyor ‘dummy’ messages, using the OTT connection 52 while it monitorspropagation times, errors etc.

Thus, in some embodiments, the host computer 24 includes processingcircuitry 42 configured to provide user data and a communicationinterface 40 that is configured to forward the user data to a cellularnetwork for transmission to the WD 22. In some embodiments, the cellularnetwork also includes the network node 16 with a radio interface 62. Insome embodiments, the network node 16 is configured to, and/or thenetwork node's 16 processing circuitry 68 is configured to perform thefunctions and/or methods described herein forpreparing/initiating/maintaining/supporting/ending a transmission to theWD 22, and/or preparing/terminating/maintaining/supporting/ending inreceipt of a transmission from the WD 22.

In some embodiments, the host computer 24 includes processing circuitry42 and a communication interface 40 configured to receive user dataoriginating from a transmission from a WD 22 to a network node 16. Insome embodiments, the WD 22 is configured to, and/or comprises a radiointerface 82 and/or processing circuitry 84 configured to perform thefunctions and/or methods described herein forpreparing/initiating/maintaining/supporting/ending a transmission to thenetwork node 16, and/orpreparing/terminating/maintaining/supporting/ending in receipt of atransmission from the network node 16.

Although FIGS. 6 and 7 show various “units” such as configuration unit32, and timer controller unit 34 as being within a respective processor,it is contemplated that these units may be implemented such that aportion of the unit is stored in a corresponding memory within theprocessing circuitry. In other words, the units may be implemented inhardware or in a combination of hardware and software within theprocessing circuitry.

FIG. 8 is a flowchart of an exemplary process in a network node 16 forhandling of reject wait time according to some embodiments of thepresent disclosure. One or more Blocks and/or functions and/or methodsperformed by the network node 16 may be performed by one or moreelements of network node 16 such as by configuration unit 32 inprocessing circuitry 68, processor 70, radio interface 62, etc.according to the example method. The method includes receiving (blockS134), from a WD 22, such as via configuration unit 32, processingcircuitry 68 and/or radio interface 62, a resume request message. Themethod includes determining (block S136), such as via configuration unit32, processing circuitry 68 and/or radio interface 62, one of a releasemessage and a suspend message to be communicated to the WD 22 as aresult of receiving the resume request message, the one of the releasemessage and the suspend message configuring a wait timer of the WD 22.

In some embodiments, the one of the release message and the suspendmessage is one of a Radio Resource Control, RRC, Release message and aRRC Suspend message. In some embodiments, the wait timer is a T302timer. In some embodiments, determining the one of the release messageand the suspend message to configure the wait timer of the WD 22 furthercomprises: configuring, such as via configuration unit 32, processingcircuitry 68 and/or radio interface 62, the wait timer of the WD 22 tostop responsive to receipt of the one of the release message and thesuspend message. In some embodiments, determining the one of the releasemessage and the suspend message to configure the wait timer of the WD 22further comprises: configuring, such as via configuration unit 32,processing circuitry 68 and/or radio interface 62, the wait timer of theWD 22 to update the wait timer according to a wait value included in theone of the release message and the suspend message.

In some embodiments, determining the one of the release message and thesuspend message to configure the wait timer of the WD 22 furthercomprises: configuring, such as via configuration unit 32, processingcircuitry 68 and/or radio interface 62, the wait timer of the WD 22 tostop responsive to identifying an indicator within the one of therelease message and the suspend message, the indicator indicating thatthe wait timer should be stopped if running. In some embodiments,determining the one of the release message and the suspend message toconfigure the wait timer of the WD 22 further comprises: configuring,such as via configuration unit 32, processing circuitry 68 and/or radiointerface 62, the wait timer of the WD 22 to stop responsive toidentifying an absence of an indicator within the one of the releasemessage and the suspend message, the indicator indicating that the waittimer should continue running if already running. In some embodiments,determining the one of the release message and the suspend message toconfigure the wait timer of the WD 22 further comprises: configuring,such as via configuration unit 32, processing circuitry 68 and/or radiointerface 62, the wait timer of the WD to restart the wait timerresponsive to receipt of the one of the release message and the suspendmessage. In some embodiments, the method further comprises, as a resultof receiving the resume request message, communicating, such as viaconfiguration unit 32, processing circuitry 68 and/or radio interface62, the one of the release message and the suspend message to the WD 22.

FIG. 9 is a flowchart of an exemplary process in a wireless device 22according to some embodiments of the present disclosure. One or moreBlocks and/or functions and/or methods performed by WD 22 may beperformed by one or more elements of WD 22 such as by timer controllerunit 34 in processing circuitry 84, processor 86, radio interface 82,etc. The method includes the WD 22 receiving (block S138), from anetwork node 16, such as via timer controller unit 23, processingcircuitry 84, and/or radio interface 82, one of a release message and asuspend message. The method includes updating (block S140), such as viatimer controller unit 23, processing circuitry 84, and/or radiointerface 82, a wait timer as a result of receiving the one of therelease message and the suspend message.

In some embodiments, the wait timer is a T302 timer. In someembodiments, updating the wait timer as a result of receiving the one ofthe release message and the suspend message further comprises: stopping,such as via timer controller unit 23, processing circuitry 84, and/orradio interface 82, the wait timer responsive to receipt of the one ofthe release message and the suspend message. In some embodiments,updating the wait timer as a result of receiving the one of the releasemessage and the suspend message further comprises: updating, such as viatimer controller unit 23, processing circuitry 84, and/or radiointerface 82, the wait timer according to a wait value identified in theone of the release message and the suspend message. In some embodiments,updating the wait timer as a result of receiving the one of the releasemessage and the suspend message further comprises: stopping, such as viatimer controller unit 23, processing circuitry 84, and/or radiointerface 82, the wait timer responsive to identifying an indicatorwithin the one of the release message and the suspend message, theindicator indicating that the wait timer should be stopped if running.

In some embodiments, updating the wait timer as a result of receivingthe one of the release message and the suspend message furthercomprises: stopping, such as via timer controller unit 23, processingcircuitry 84, and/or radio interface 82, the wait timer responsive toidentifying an absence of an indicator within the one of the releasemessage and the suspend message, the indicator indicating that the waittimer should continue running if already running. In some embodiments,updating the wait timer as a result of receiving the one of the releasemessage and the suspend message further comprises: restarting, such asvia timer controller unit 23, processing circuitry 84, and/or radiointerface 82, the wait timer responsive to receipt of the one of therelease message and the suspend message. In some embodiments, the one ofthe release message and the suspend message is one of a Radio ResourceControl, RRC, Release message and a RRC Suspend message. In someembodiments, the method further comprises communicating, such as viatimer controller unit 23, processing circuitry 84, and/or radiointerface 82, to the network node 16, a resume request message, whereinthe one of the release message and the suspend message is received as aresult of communicating the resume request message.

FIG. 10 is a flowchart of an yet another exemplary process in a wirelessdevice 22 according to some embodiments of the present disclosure. Oneor more Blocks and/or functions and/or methods performed by WD 22 may beperformed by one or more elements of WD 22 such as by timer controllerunit 34 in processing circuitry 84, processor 86, radio interface 82,etc. The method includes the WD 22 detecting (block S142), such as viatimer controller unit 34, processing circuitry 84 and/or radio interface82, an integrity protection verification error in a lower layer while await timer is running. The method includes updating (block S144), suchas via timer controller unit 34, processing circuitry 84 and/or radiointerface 82, the wait timer as a result of the detection of theintegrity protection verification error.

In some embodiments, the wait timer is a T302 timer. In someembodiments, updating the wait timer as a result of the detection of theintegrity protection verification error further comprises: stopping,such as via timer controller unit 34, processing circuitry 84 and/orradio interface 82, the wait timer responsive to the detection of theintegrity protection verification error. In some embodiments, updatingthe wait timer as a result of the detection of the integrity protectionverification error further comprises: restarting, such as via timercontroller unit 34, processing circuitry 84 and/or radio interface 82,the wait timer responsive to the detection of the integrity protectionverification error. In some embodiments, detecting the integrityprotection verification error in the lower layer while the wait timer isrunning further comprises at least one of: detecting, such as via timercontroller unit 34, processing circuitry 84 and/or radio interface 82,that a T300X timer expired and detecting an integrity check failurewhile the T300X timer is running.

Having described some embodiments of the present disclosure, a moredetailed description of some of the embodiments follows.

Some embodiments of the present disclosure may be based on introducingnew triggers/mechanisms for stopping/updating the wait timer T302. Inaddition to existing cases when the timer T302 is stopped in LTE (uponentering RRC_CONNECTED, i.e., when the WD 22 receives a Resume messageor an RRC Setup message), in some embodiments of the present disclosurethe timer is also stopped in the following novel cases when the WD 22 isperforming the resume procedure (e.g. when the WD 22 has sent aResumeRequest message):

-   -   When the WD 22 receives the Suspend message;    -   When the WD 22 receives the Release message; and/or    -   When the WD 22 has detected an integrity protection verification        error in lower layers (e.g., Packet Data Convergence Protocol        (PDCP) layer) while timer T302 or T300/T300X (these timers are        started when WD 22 sends a Resume request message) is running.

In a first embodiment, WD 22 may stop a wait timer (e.g., timer T302),if running, upon the reception of an RRC Release message (from e.g.,network node 16) in response to an RRC Resume Request transmitted (e.g.,by the WD 22 to the network node 16) while the wait timer (e.g., T302)is running.

In a second embodiment, WD 22 may stop a wait timer (e.g., T302), ifrunning, upon the reception of an RRC Suspend message (from e.g.,network node 16) in response to an RRC Resume Request transmitted (e.g.,by the WD 22 to the network node 16) while the wait timer (e.g., T302)is running. In a variant of this second embodiment, WD 22 may stop thewait timer (e.g., T302), if running, upon the reception of an RRCRelease message (containing a suspend indication) (from e.g., networknode 16) in response to an RRC Resume Request (e.g., by the WD 22 to thenetwork node 16) transmitted while the wait timer (e.g., T302) isrunning.

In a third embodiment, the WD 22 may stop the timer upon receiving aspecified indication in the Suspend or Release message or Releasemessage (with suspend configuration) that the wait timer (e.g., T302)should be stopped if running.

In a fourth embodiment, the WD 22 may stop the timer upon the absence ofa specified indication in the Suspend message or Release message orRelease message (with suspend configuration) that the wait timer (e.g.,T302) should be maintained if running.

In a fifth embodiment, the WD 22 receives (e.g., from network node 16) avalue of wait time in a Suspend or Release message (sent in response toa Resume Request message from the WD 22), while the wait timer (e.g.,T302) is running, and the WD 22 may perform an updating operation e.g.,the WD 22 may apply the new value and start the wait timer (e.g., T302)according to the newly received value.

In a sixth embodiment, the WD 22 may reset or restart the timer (e.g.,T302) when receiving a Suspend or Release message (in response to aResume Request).

In a seventh embodiment, the WD 22 may detect an integrity protectionverification error in lower layers (e.g., PDCP layer) while timer (e.g.,T302 or T300/T300X) is running and the WD 22 may either stop timer, orrestart timer.

The above embodiments above can also be combined in any form in furtheraspects of the disclosure.

EXAMPLE IMPLEMENTATIONS OF SOME OF THE EMBODIMENTS OF THE DISCLOSUREExample Implementation of First and Second Embodiments

In accordance with one example of the first embodiment, as a result ofthe WD 22 receiving an RRCRelease message (e.g., from the network node16), the WD 22 may perform the following:

-   -   (a) discard any stored WD 22 AS context and I-RNTI;    -   (b) stop the timer T302 if the timer is running;    -   (c) delay the following actions defined in this sub-clause X ms        (the value of X may be configurable or may be fixed to e.g., 60        ms) from the moment the RRCRelease message was received or        optionally when lower layers indicate that the receipt of the        RRCRelease message has been successfully acknowledged, whichever        is earlier.

In accordance with one example of the second embodiment, as a result ofthe WD 22 receiving an RRCSuspend message (e.g., from the network node16), the WD 22 may perform the following:

-   -   (a) delay the following actions defined in this sub-clause for X        ms (the value of X may be configurable or may be fixed to e.g.,        60 ms) from the moment the RRCSuspend message was received or        optionally when lower layers indicate that the receipt of the        RRCSuspend message has been successfully acknowledged, whichever        is earlier;    -   (b) stop the timer T302 if the timer is running;    -   (c) if the RRCSuspend message includes the        idleModeMobilityControlInfo:        -   (i) store the cell reselection priority information provided            by the idleModeMobilityControlInfo;        -   (ii) if the t320 is included: start timer T320, with the            timer value set according to the value of t320;    -   (d) else: apply the cell reselection priority information        broadcast in the system information;    -   (e) store the following information provided by the network:        resumeIdentity, nextHopChainingCount, ran-PagingCycle and        ran-NotificationAreaInfo;    -   (f) re-establish Radio Link Control (RLC) entities for all        Signalling Radio Bearers (SRBs) and Data Radio Bearers (DRBs);    -   (g) except if the RRCSuspend message was received in response to        an RRCResumeRequest: store the WD 22 AS Context including the        current RRC configuration, the current security context, the        PDCP state including Robust Header Compression (ROHC) state,        C-RNTI used in the source Primary Cell (PCell), the cellIdentity        and the physical cell identity of the source PCell;    -   (h) suspend all SRB(s) and DRB(s), except SRB0;    -   (i) start timer T380, with the timer value set to periodic-RNA        U-timer;    -   (j) indicate the suspension of the RRC connection to upper        layers;    -   (k) configure lower layers to suspend integrity protection and        ciphering; and    -   (l) enter RRC_INACTIVE and perform procedures as specified in TS        38.304.

The following is an example table, Table 2, illustrating an exampletimer according to an embodiment of the present disclosure. Inparticular, Table 2 indicates what may start the timer, what may stopthe timer and what can occur at the expiration of the timer, as follows:

TABLE 2 Timer Start Stop At expiry T302 Reception of Upon enteringInform upper RRCReject while RRC_CONNECTED, layers about performing RRCupon receiving barring alleviation connection RRCRelease or as specifiedin establishment or RRCSuspend and 5.3.x. resume. upon cellre-selection.

Example Implementation of Third Embodiment

According to one example of the third embodiment, the WD 22 may stop thewait timer upon receiving a specified indication in the Suspend orRelease message or Release message (with suspend configuration) that thewait timer T302 shall be stopped if running. Otherwise, if theindication is not present, the WD 22 does not stop the timer. Accordingto such example, as a result of the WD 22 receiving an RRCSuspendmessage (e.g., from the network node 16), the WD 22 may perform thefollowing:

-   -   a) delay the following actions defined in this sub-clause X ms        (the value of X may be configurable or may be fixed to e.g., 60        ms) from the moment the RRCSuspend message was received or        optionally when lower layers indicate that the receipt of the        RRCSuspend message has been successfully acknowledged, whichever        is earlier    -   b) if the RRCSuspend message includes an indication to stop the        timer T302, stop the timer T302 if running;    -   c) if the RRCSuspend message includes the        idleModeMobilityControlInfo:        -   (1) store the cell reselection priority information provided            by the idleModeMobilityControlInfo;        -   (2) if the t320 is included: start timer T320, with the            timer value set according to the value of t320;    -   d) else:        -   (1) apply the cell reselection priority information            broadcast in the system information;    -   e) store the following information provided by the network:        resumeIdentity, nextHopChainingCount, ran-PagingCycle and        ran-NotificationAreaInfo;    -   f) re-establish RLC entities for all SRBs and DRBs;    -   g) except if the RRCSuspend message was received in response to        an RRCResumeRequest:        -   (1) store the WD 22 AS Context including the current RRC            configuration, the current security context, the PDCP state            including ROHC state, C-RNTI used in the source PCell, the            cellIdentity and the physical cell identity of the source            PCell;    -   h) suspend all SRB(s) and DRB(s), except SRB0;    -   i) start timer T380, with the timer value set to periodic-RNA        U-timer;    -   j) indicate the suspension of the RRC connection to upper        layers;    -   k) configure lower layers to suspend integrity protection and        ciphering;    -   l) enter RRC_INACTIVE and perform procedures as specified in TS        38.304

According to another example of the third embodiment, as a result of theWD 22 receiving an RRCRelease message (e.g., from the network node 16),the WD 22 may perform the following:

-   -   a) discard any stored WD 22 AS context and I-RNTI;    -   b) if the RRCRelease message includes an indication to stop the        timer T302, stop the timer T302 if running;    -   c) delay the following actions defined in this sub-clause X ms        (the value of X may be configurable or may be fixed to e.g., 60        ms) from the moment the RRCRelease message was received or        optionally when lower layers indicate that the receipt of the        RRCRelease message has been successfully acknowledged, whichever        is earlier;

Example Implementation of Fourth Embodiment

According to one example of the fourth embodiment, the WD 22 may stopthe timer upon the absence of a specified indication in the Suspendmessage or Release message or Release message (with suspendconfiguration) that the wait timer T302 shall be stopped if running.According to this example, as a result of the WD 22 receiving (e.g.,from the network node 16) a RRCSuspend, the WD 22 may perform thefollowing:

-   -   a) delay the following actions defined in this sub-clause X ms        (the value of X may be configurable or may be fixed to e.g., 60        ms) from the moment the RRCSuspend message was received or        optionally when lower layers indicate that the receipt of the        RRCSuspend message has been successfully acknowledged, whichever        is earlier;    -   b) if the RRCSuspend message does not include includes an        indication to maintain the timer T302, stop the timer T302 if        running;    -   c) if the RRCSuspend message includes the        idleModeMobilityControlInfo:        -   (1) store the cell reselection priority information provided            by the idleModeMobilityControlInfo;        -   (2) if the t320 is included: start timer T320, with the            timer value set according to the value of t320;    -   d) else:        -   (1) apply the cell reselection priority information            broadcast in the system information;    -   e) store the following information provided by the network:        resumeIdentity, nextHopChainingCount, ran-PagingCycle and        ran-NotificationAreaInfo;    -   f) re-establish RLC entities for all SRBs and DRBs;    -   g) except if the RRCSuspend message was received in response to        an RRCResumeRequest:        -   (1) store the WD 22 AS Context including the current RRC            configuration, the current security context, the PDCP state            including ROHC state, C-RNTI used in the source PCell, the            cellIdentity and the physical cell identity of the source            PCell;    -   h) suspend all SRB(s) and DRB(s), except SRB0;    -   i) start timer T380, with the timer value set to periodic-RNA        U-timer;    -   j) indicate the suspension of the RRC connection to upper        layers;    -   k) configure lower layers to suspend integrity protection and        ciphering;    -   l) enter RRC_INACTIVE and perform procedures as specified in TS        38.304.

According to another example of the fourth embodiment, as a result ofthe WD 22 receiving (e.g., from the network node 16) a RRCRelease, theWD 22 may perform the following:

-   -   a) discard any stored WD 22 AS context and I-RNTI;    -   b) if the RRCRelease message includes an indication to maintain        the timer T302, stop the timer T302 if running;    -   c) delay the following actions defined in this sub-clause X ms        (the value of X may be configurable or may be fixed to e.g., 60        ms) from the moment the RRCRelease message was received or        optionally when lower layers indicate that the receipt of the        RRCRelease message has been successfully acknowledged, whichever        is earlier;

Example Implementation of Fifth Embodiment

According to one example of a fifth embodiment, the WD 22 receives avalue of a wait time in a Suspend or Release message (e.g., from thenetwork node 16) (in response to a Resume Request), while the wait timerT302 is running, and performs an updating operation i.e., the WD 22applies the new value and starts the wait timer T302 according to thenewly received value. In accordance with this example, as a result ofthe WD 22 receiving (e.g., from the network node 16) a RRCSuspend, theWD 22 may perform the following:

-   -   a) delay the following actions defined in this sub-clause X ms        (the value of X may be configurable or may be fixed to e.g., 60        ms) from the moment the RRCSuspend message was received or        optionally when lower layers indicate that the receipt of the        RRCSuspend message has been successfully acknowledged, whichever        is earlier    -   b) if the RRCSuspend message does includes a wait time;        -   (1) set timer T302 to the value of the wait time;        -   (2) start timer T302;    -   c) if the RRCSuspend message includes the        idleModeMobilityControlInfo:        -   (1) store the cell reselection priority information provided            by the idleModeMobilityControlInfo;        -   (2) if the t320 is included: start timer T320, with the            timer value set according to the value of t320;    -   d) else:        -   (1) apply the cell reselection priority information            broadcast in the system information;    -   e) store the following information provided by the network:        resumeIdentity, nextHopChainingCount, ran-PagingCycle and        ran-NotificationAreaInfo;    -   f) re-establish RLC entities for all SRBs and DRBs;    -   g) except if the RRCSuspend message was received in response to        an RRCResumeRequest:        -   (1) store the WD 22 AS Context including the current RRC            configuration, the current security context, the PDCP state            including ROHC state, C-RNTI used in the source PCell, the            cellIdentity and the physical cell identity of the source            PCell;    -   h) suspend all SRB(s) and DRB(s), except SRB0;    -   i) start timer T380, with the timer value set to periodic-RNA        U-timer;    -   j) indicate the suspension of the RRC connection to upper        layers;    -   k) configure lower layers to suspend integrity protection and        ciphering;    -   l) enter RRC_INACTIVE and perform procedures as specified in TS        38.304 [21].

According to another example of the fifth embodiment, as a result of theWD 22 receiving (e.g., from network node 16) a RRCRelease, the WD 22 mayperform the following:

-   -   a) discard any stored WD 22 AS context and I-RNTI;    -   b) if the RRCRelease message does includes a wait time;        -   (1) set timer T302 to the value of the wait time;        -   (2) start timer T302;    -   c) delay the following actions defined in this sub-clause X ms        from the moment the RRCRelease message was received or        optionally when lower layers indicate that the receipt of the        RRCRelease message has been successfully acknowledged, whichever        is earlier;

Example Implementation of Sixth Embodiment

According to one example of a sixth embodiment, the WD 22 resets orrestart the timer T302 when receiving a Suspend or Release message(e.g., form a network node 16) (in response to a Resume Request). In anexample, as a result of the WD 22 receiving a RRCSuspend message, the WD22 may perform the following:

-   -   a) delay the following actions defined in this sub-clause X ms        from the moment the RRCSuspend message was received or        optionally when lower layers indicate that the receipt of the        RRCSuspend message has been successfully acknowledged, whichever        is earlier;    -   b) restart timer T302 if running;    -   c) if the RRCSuspend message includes the        idleModeMobilityControlInfo:        -   store the cell reselection priority information provided by            the idleModeMobilityControlInfo;        -   (1) if the t320 is included: start timer T320, with the            timer value set according to the value of t320;    -   d) else:        -   (1) apply the cell reselection priority information            broadcast in the system information;    -   e) store the following information provided by the network:        resumeIdentity, nextHopChainingCount, ran-PagingCycle and        ran-NotificationAreaInfo;    -   f) re-establish RLC entities for all SRBs and DRBs;    -   g) except if the RRCSuspend message was received in response to        an RRCResumeRequest:        -   (1) store the WD 22 AS Context including the current RRC            configuration, the current security context, the PDCP state            including ROHC state, C-RNTI used in the source PCell, the            cellIdentity and the physical cell identity of the source            PCell;    -   h) suspend all SRB(s) and DRB(s), except SRB0;    -   i) start timer T380, with the timer value set to periodic-RNA        U-timer;    -   j) indicate the suspension of the RRC connection to upper        layers;    -   k) configure lower layers to suspend integrity protection and        ciphering;    -   l) enter RRC_INACTIVE and perform procedures as specified in TS        38.304.

In another example of the sixth embodiment, as a result of the WD 22receiving a RRCRelease message, the WD 22 may perform the following:

-   -   a) discard any stored WD 22 AS context and I-RNTI;    -   b) restart T302 if running; and    -   c) delay the following actions defined in this sub-clause X ms        from the moment the RRCRelease message was received or        optionally when lower layers indicate that the receipt of the        RRCRelease message has been successfully acknowledged, whichever        is earlier.

Example Implementation of Seventh Embodiment

In one example of a seventh embodiment, the WD 22 detects an integrityprotection verification error in lower layers (e.g., PDCP layer) whiletimer T302 or T300/T300X is running and either stops time T302 orrestarts timer T302. According to one example, the WD 22 may detect thata T300X timer has expired or may detect an integrity check failure fromlower layers while T300X is running. As a result, the WD 22 may performthe following:

-   -   a) stop T302 if running; and    -   b) if timer T300X expires or upon receiving Integrity check        failure indication: perform the actions upon going to RRC_IDLE        as specified in 5.3.11 with release cause RRC Resume failure.

In some embodiments, configuring a terminal or wireless device or nodemay involve instructing and/or causing the wireless device or node tochange its configuration, e.g., at least one setting and/or registerentry and/or operational mode. A terminal or wireless device or node maybe adapted to configure itself, e.g., according to information or datain a memory of the terminal or wireless device. Configuring a node orterminal or wireless device by another device or node or a network mayrefer to and/or comprise transmitting information and/or data and/orinstructions to the wireless device or node by the other device or nodeor the network, e.g., allocation data (which may also be and/or compriseconfiguration data) and/or scheduling data and/or scheduling grants.Configuring a terminal may include sending RRC messages to the terminalindicating parameters for, e.g., a wait timer according to embodimentsof the present disclosure.

Configuring a Radio Node

Configuring a radio node, in particular a terminal or user equipment orthe WD 22, may refer to the radio node being adapted or caused or setand/or instructed to operate according to the configuration. Configuringmay be done by another device, e.g., a network node 16 (for example, aradio node of the network like a base station or eNodeB) or network, inwhich case it may comprise transmitting configuration data to the radionode to be configured. A radio node may configure itself, e.g., based onconfiguration data received from a network or network node 16. A networknode 16 may use, and/or be adapted to use, its circuitry/ies forconfiguring. Configuration data may comprise and/or be represented byconfiguration information, and/or one or more corresponding indicationsand/or message/s.

Configuring in General

Generally, configuring may include determining configuration datarepresenting the configuration and providing, e.g. transmitting, it toone or more other nodes (parallel and/or sequentially), which maytransmit it further to the radio node (or another node, which may berepeated until it reaches the wireless device 22). Alternatively, oradditionally, configuring a radio node, e.g., by a network node 16 orother device, may include receiving configuration data and/or datapertaining to configuration data, e.g., from another node like a networknode 16, which may be a higher-level node of the network, and/ortransmitting received configuration data to the radio node. Accordingly,determining a configuration and transmitting the configuration data tothe radio node may be performed by different network nodes or entities,which may be able to communicate via a suitable interface, e.g., an X2interface in the case of LTE or a corresponding interface for NR.Configuring a terminal (e.g. WD 22) may comprise scheduling downlinkand/or uplink transmissions for the terminal, e.g. downlink data and/ordownlink control signaling and/or DCI and/or uplink control or data orcommunication signaling, in particular acknowledgement signaling, and/orconfiguring resources and/or a resource pool therefor. In particular,configuring a terminal (e.g. WD 22) may comprise configuring the WD 22to update a wait timer according to embodiments of the presentdisclosure.

As will be appreciated by one of skill in the art, the conceptsdescribed herein may be embodied as a method, data processing system,computer program product and/or computer storage media storing anexecutable computer program. Accordingly, the concepts described hereinmay take the form of an entirely hardware embodiment, an entirelysoftware embodiment or an embodiment combining software and hardwareaspects all generally referred to herein as a “circuit” or “module.” Anyprocess, step, action and/or functionality described herein may beperformed by, and/or associated to, a corresponding module, which may beimplemented in software and/or firmware and/or hardware. Furthermore,the disclosure may take the form of a computer program product on atangible computer usable storage medium having computer program codeembodied in the medium that can be executed by a computer. Any suitabletangible computer readable medium may be utilized including hard disks,CD-ROMs, electronic storage devices, optical storage devices, ormagnetic storage devices.

Some embodiments are described herein with reference to flowchartillustrations and/or block diagrams of methods, systems and computerprogram products. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer (to therebycreate a special purpose computer), special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

These computer program instructions may also be stored in a computerreadable memory or storage medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer readablememory produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks mayoccur out of the order noted in the operational illustrations. Forexample, two blocks shown in succession may in fact be executedsubstantially concurrently or the blocks may sometimes be executed inthe reverse order, depending upon the functionality/acts involved.Although some of the diagrams include arrows on communication paths toshow a primary direction of communication, it is to be understood thatcommunication may occur in the opposite direction to the depictedarrows.

Computer program code for carrying out operations of the conceptsdescribed herein may be written in an object oriented programminglanguage such as Java® or C++. However, the computer program code forcarrying out operations of the disclosure may also be written inconventional procedural programming languages, such as the “C”programming language. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer. In the latter scenario, theremote computer may be connected to the user's computer through a localarea network (LAN) or a wide area network (WAN), or the connection maybe made to an external computer (for example, through the Internet usingan Internet Service Provider).

Many different embodiments have been disclosed herein, in connectionwith the above description and the drawings. It will be understood thatit would be unduly repetitious and obfuscating to literally describe andillustrate every combination and subcombination of these embodiments.Accordingly, all embodiments can be combined in any way and/orcombination, and the present specification, including the drawings,shall be construed to constitute a complete written description of allcombinations and subcombinations of the embodiments described herein,and of the manner and process of making and using them, and shallsupport claims to any such combination or subcombination.

As will be appreciated by one of skill in the art, the conceptsdescribed herein may be embodied as a method, data processing system,and/or computer program product. Accordingly, the concepts describedherein may take the form of an entirely hardware embodiment, an entirelysoftware embodiment or an embodiment combining software and hardwareaspects all generally referred to herein as a “circuit” or “module.”Furthermore, the disclosure may take the form of a computer programproduct on a tangible computer usable storage medium having computerprogram code embodied in the medium that can be executed by a computer.Any suitable tangible computer readable medium may be utilized includinghard disks, CD-ROMs, electronic storage devices, optical storagedevices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchartillustrations and/or block diagrams of methods, systems and computerprogram products. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable memory or storage medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer readablememory produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks. It is to beunderstood that the functions/acts noted in the blocks may occur out ofthe order noted in the operational illustrations. For example, twoblocks shown in succession may in fact be executed substantiallyconcurrently or the blocks may sometimes be executed in the reverseorder, depending upon the functionality/acts involved. Although some ofthe diagrams include arrows on communication paths to show a primarydirection of communication, it is to be understood that communicationmay occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the conceptsdescribed herein may be written in an object oriented programminglanguage such as Java® or C++. However, the computer program code forcarrying out operations of the disclosure may also be written inconventional procedural programming languages, such as the “C”programming language. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer. In the latter scenario, theremote computer may be connected to the user's computer through a localarea network (LAN) or a wide area network (WAN), or the connection maybe made to an external computer (for example, through the Internet usingan Internet Service Provider).

Many different embodiments have been disclosed herein, in connectionwith the above description and the drawings. It will be understood thatit would be unduly repetitious and obfuscating to literally describe andillustrate every combination and subcombination of these embodiments.Accordingly, all embodiments can be combined in any way and/orcombination, and the present specification, including the drawings,shall be construed to constitute a complete written description of allcombinations and subcombinations of the embodiments described herein,and of the manner and process of making and using them, and shallsupport claims to any such combination or subcombination.

It will be appreciated by persons skilled in the art that theembodiments described herein are not limited to what has beenparticularly shown and described herein above. In addition, unlessmention was made above to the contrary, it should be noted that all ofthe accompanying drawings are not to scale. A variety of modificationsand variations are possible in light of the above teachings withoutdeparting from the scope of the following claims.

What is claimed is:
 1. A method in a wireless device configured tocommunicate with a network node in a wireless communication system, themethod comprising: transmitting a resume request to the network node;responsive to the transmitting of the resume request, receiving a firstindication from the network node, the first indication being one of asuspend message and a release message, the first indication beingreceived while a wait timer is running, the first indication includingan indication of a wait time value; and updating the wait timeraccording to the indicated wait time value.
 2. The method of claim 1,wherein the wait timer is a T302 timer.
 3. The method of claim 1,wherein the resume request is an RRC resume request, the suspend messagebeing an RRC suspend message and the release message being an RRCrelease message.
 4. The method of claim 1, wherein updating the waittimer includes starting the wait timer with the wait time valueindicated in the received first indication.
 5. The method of claim 1,wherein the method further comprises starting the wait timer at a firsttime, the first indication being received subsequent to the first time.6. The method of claim 5, wherein: the method further comprisesreceiving a reject message from the network node while performing one ofa connection establishment procedure and a connection resume procedurewith the network node; the starting of the wait timer being triggered atthe first time by the receiving of the reject message; and the resumerequest being transmitted subsequent to the receiving of the rejectmessage.
 7. A wireless device configured to communicate with a networknode in a wireless communication system, the wireless device comprisingprocessing circuitry configured to: cause transmission of a resumerequest to the network node; responsive to the transmitting of theresume request, receive a first indication from the network node, thefirst indication being one of a suspend message and a release message,the first indication being received while a wait timer is running, thefirst indication including an indication of a wait time value; andupdate the wait timer according to the indicated wait time value.
 8. Thewireless device of claim 7, wherein the wait timer is a T302 timer. 9.The wireless device of claim 7, wherein the resume request is an RRCresume request, the suspend message being an RRC suspend message and therelease message being an RRC release message.
 10. The wireless device ofclaim 7, wherein updating the wait timer includes starting the waittimer with the wait time value indicated in the received firstindication.
 11. The wireless device of claim 7, wherein the processingcircuitry is further configured to: start the wait timer at a firsttime, the first indication being received subsequent to the first time.12. The wireless device of claim 11, wherein: the processing circuitryis further configured to receive a reject message from the network nodewhile performing one of a connection establishment procedure and aconnection resume procedure with the network node; the starting of thewait timer being triggered at the first time by the receiving of thereject message; and the resume request being transmitted subsequent tothe receiving of the reject message.
 13. A method in a network nodeconfigured to communicate with a wireless device in a wirelesscommunication system, the method comprising: receiving a resume requestfrom the wireless device; responsive to the receiving of the resumerequest, determining a first indication to be communicated to thewireless device, the first indication being one of a suspend message anda release message, the first indication being scheduled for transmissionwhile a wait timer is running, the first indication including anindication of a wait time value; and transmitting the first indicationto the wireless device, the first indication configuring the wirelessdevice to update the wait timer according to the indicated wait timevalue.
 14. The method of claim 13, wherein the wait timer is a T302timer.
 15. The method of claim 13, wherein the resume request is an RRCresume request, the suspend message being an RRC suspend message and therelease message being an RRC release message.
 16. The method of claim13, wherein the updating of the wait timer includes starting the waittimer with the wait time value indicated in the first indication. 17.The method of claim 13, wherein: the method further comprisestransmitting a reject message to the wireless device while performingone of a connection establishment procedure and a connection resumeprocedure with the wireless device; a starting of the wait timer beingtriggered at a first time by the transmitting of the reject message; andthe resume request being received subsequent to the transmitting of thereject message.